Running Exchange 2007 SP2, clients on one server are saying that they cannot connect to Exch via Outlook, either via cached or Online. OWA failing too. Test-MAPIConnectivity looks ok though and I can't see anything obvious with the server. Clients can ping the server ok. Nothing in Event Viewer. Need help?

Need to start with the basics, check to make sure all Exchange services are running and post any errors in the event logs.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

On Sat, 12 Mar 2011 18:32:54 +0000, Redman20111 wrote: > > >Running Exchange 2007 SP2, clients on one server are saying that they cannot connect to Exch via Outlook, either via cached or Online. OWA failing too. > >Test-MAPIConnectivity looks ok though and I can't see anything obvious with the server. Clients can ping the server ok. Nothing in Event Viewer. Ping just verifies that the IP stack is still alive. The entire user-mode part of the O/S could be dead and ping would still work. Two quick checks to make would be: test-systemhealth test-servicehealth If they both look good, pick one of the mailboxes that's having a problem and see if OWA and MAPI access has been disabled. Are all the databases mounted? If it all looks good up to this point, I'd try rebooting the machine. If it's still broken after that, and there's still nothing recorded in the application or system event logs you may have to resort to using rpcping and see if the GUIDs for the directory service and information store are still published in the port mapper. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I had to fail over the server, this seemed to fix it. Not sure what the problem was... "If it's still broken after that, and there's still nothing recorded in the application or system event logs you may have to resort to usingrpcping and see if the GUIDs for the directory service and information store are still published in the port mapper." I've read about rcpping ( http://support.microsoft.com/kb/831051 ) but not sure how to run it here or what I should be looking for?

On Sun, 13 Mar 2011 19:57:30 +0000, Redman20111 wrote: > > >I had to fail over the server, this seemed to fix it. > >Not sure what the problem was... > >"If it's still broken after that, and there's still nothing recorded in the application or system event logs you may have to resort to usingrpcping and see if the GUIDs for the directory service and information store are still published in the port mapper." > >I've read about rcpping ( http://support.microsoft.com/kb/831051 ) but not sure how to run it here or what I should be looking for? You'd be looking to know what it was that isn't there or not working. Trying to connect to the directory service or information store service GUID would tell you if those GUIDs were no longer present in the RPC port mapper. Testing using RPC-over-HTTPS would tell you if the problem was the CAS of if the proxy ports weren't working. All you knew when it wasn't working was that it wasn't working. You may have had something (who knows what) eat up all the TCP ports too, but that's pretty unlikely if you were able to RDP to the CMS. Using portqry.exe would probably be a faster way to see if the GUIDs were still being published: http://support.microsoft.com/kb/310298 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

HI You can use portqry to check network. You can also read this kb article. It is not about your issue. But it offer you the process of checking function of exchange 2007. http://support.microsoft.com/kb/924625

Hi Do you have anything to update your issue ?